home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
008a
/
syslog12.zip
/
SYSLOG.DOC
< prev
next >
Wrap
Text File
|
1991-09-23
|
9KB
|
265 lines
SYSLOG v1.2 USER DOCUMENTATION
Copyright (c) - Solid Oak Software Inc. 1991
Overview of Program
SYSLOG is a small ( 8K ), memory resident ( TSR ) program, that
allows the user to maintain a daily log file of activities that
take place on his or her computer. SYSLOG will automatically keep
a record of all programs run, files copied, files deleted, files
created, and files opened, as well as the date and time that each
activity occurred. SYSLOG has many potential uses including
security, productivity, diagnostics, job costing, etc. All
monitoring and logging activities are performed COMPLETELY in the
background. The user will not even be aware of it.
There are many situations where this type of logging can be
useful. If you like, you can determine how much time was spent on
a particular project by examining the log files. If you are an
employer, you might want to check the log files periodically to
determine the quantity or type of work that was done, or even
check to see if your employee was playing space invaders or
writing a letter to Aunt Jane while they were supposed to be
working.
In some business environments, activity logging can play an even
more important role. It can easily be determined if a program, or
sensitive data, was copied to a floppy disk, of if unauthorized
access was made to sensitive files or programs. Many large
corporations have policies against illegal copying of software,
and regularly check computer systems to ensure that the users are
not running programs they are not licensed to run. SYSLOG can
make that job easier, by creating records of any file that was
added to the system, or copied or removed from the system. Since
SYSLOG is active at all times, records are kept of ALL computer
activity, even after business hours, or on weekends.
Of course most expert computer operators could defeat SYSLOG, if
they knew it was installed, and what it does. In the normal
environment, however, the user would never have a clue that their
activities were being logged. SYSLOG only writes to the log file
when other disk activities are being performed. So it makes it
almost impossible to tell that it is working, even if you are
aware that it is installed.
Installation and Operation
SYSLOG is very simple to use. First of all, we recommend that it
be installed in your utility directory or other directory in your
DOS path. Secondly, SYSLOG is date and time sensitive, so the
date and time must be set to the correct values prior to
installing the program.
You may install SYSLOG.EXE in any directory you wish, and either
add the directory to your DOS path, or call the program from your
autoexec file in the format \< directory >\SYSLOG.
It is recommended that you call SYSLOG from your autoexec.bat
file. SYSLOG creates a new log file for each day. All log files
have the extension SOS, are kept in the C:\SYSLOG.DAT directory,
which is automatically created. The file name is created from the
current date. For example SEPTEMBER 18, 1991 would generate the
file name 09181991.SOS. This allows easy identification of a
particular file. The log files created are simple ASCII files,
and can be viewed with any editor or word processor. Site license
users will receive a special reader that will allow the use of
hidden log files.
SYSLOG has five possible optional command line parameters:
SYSLOG /o = Enable OPEN FILE logging. ( Can create VERY large
log files )
SYSLOG /s = Silent mode. ( No loading message. User doesn't know
it's loading )*
SYSLOG /r = Produces READ-ONLY files that cannot be erased or
edited.
SYSLOG /h = Produces HIDDEN files.
SYSLOG /d = Removes SYSLOG from memory.
* Not functional in the shareware version.
Note: When you remove SYSLOG from memory, the current log file is
left in a normal state. If you want it to remain READ-ONLY or
HIDDEN, add the appropriate parameter when de-installing the
program. For example SYSLOG /D/H will de-install SYSLOG and leave
the log file as a hidden file.
Important Considerations
IMPORTANT: CERTAIN PROGRAMS SHOULD NOT BE RUN WHILE SYSLOG IS
ACTIVE. THEY COULD CAUSE SERIOUS PROBLEMS OR CAUSE THE SYSTEM TO
"HANG" AND NEED TO BE REBOOTED.
Disk optimization and unfragmenting programs.
Disk diagnostic programs.
High speed tape and disk backup programs.
If you are running SYSLOG in a situation where the operator is
unaware of its operation and you there is a possibility that any
of the these program types will be run, you can still allow the
user access to these programs if you use the following procedure:
For instance, if you wanted to run Norton Speed Disk on a regular
basis, you could run it safely like this:
First, RENAME SD.EXE _SD.EXE
Then create this batch file called SD.BAT.
SYSLOG /D
_SD%1
SYSLOG
This will unload SYSLOG before running Speed Disk, then reload it
afterwards. This method can be used to run almost any utility
without problems.
Any suggestions or comments would be greatly appreciated.
Solid Oak Software Inc.
PO Box 31004
Santa Barbara, CA 93130
805-682-3202 FAX 805-569-0451
Modification History
Version 1.1
Calling program with /d option will not install if SYSLOG not
active in memory.
SYSLOG log file directory C:\SYSLOG.DAT now automatically
created.
Log entry is created when time is changed.
Log entry is created when directories are created or removed.
Version 1.2
New log file is created if syslog is active at midnight.
Three new EXE files have been added to the package in an effort
to make the system more versatile.
SYSLOGT.EXE: This program is slightly larger and takes about 1K
more memory. It has the added capability of logging periods of
keyboard inactivity in 15 minute increments. This is done even
if another application is loaded and active. Since this version
of the program traps both the keyboard and timer interrupts, some
speed degradation or software incompatibilities might be noticed,
so it should only be used when this feature is desired. All
command line parameters are the same as SYSLOG.
TIMELOG.EXE: This program incorporates only the logging
capabilities for keyboard inactivity. It performs the same
functions as SYSLOGT. The /O command line parameter does not
apply.
SYSLOG, SYSLOGT, and TIMELOG must be used independently. You
should run only ONE of these programs at a time.
LOGENTRY.EXE: This program lets you manually create a log entry.
It is NOT memory resident. This is useful in batch files where a
process begin and end times may wish to be logged. To use the
Norton Speed Disk example, the usage would be as follows:
SYSLOG /D
LOGENTRY Norton Speed Disk initiated
_SD%1
LOGENTRY Norton Speed Disk completed
SYSLOG
LOGENTRY maintains the file attribute of the current logfile (
normal, read-only, or hidden ). LOGENTRY can also be used stand
alone if desired as it creates the log file automatically.